2015-10-02 - 22020 - Spec - Discount Override by SO Created On (Dan by 2015-10-29) #US #OrderEntry #abapquality #salesorders #SDSupportOrderEntry

SPECIFICATIONS

22020-Spec- Discount Override by SO Created On


Purpose


Particular discount should be override with another discount in the sales order with the value based on order creation date.

Admin Info


Purpose
Particular discount should be override with another discount in the sales order with the value based on order creation date.
Requested By
Daniel Brennan
Spec Created By
Deepak Yasam
Spec Created Date
10/02/2015
Spec QA by
Surya Basa
Objects
A525
VVC_T682_VA

V_T683

V_T685A
Document Status
Completed


Estimates



Sl.No
Activity
Estimation in Hours
1
Research
04
2
Documentation
04
3
Development/ Config
8
4
Unit test in DEV
10
5
Unit test in QUA
00
6
Other activity


TOTAL
26

References


Prior Tickets

[Provide links of prior associated Spec / Break Fix BOSS document(s)]

None

Documents

[Attach any document(s) received for the requirement(s)]

None


Spec Changes


[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]

Sl.
Change Details
Requested By
Requested On
Notes if any
1
Add new field to ROC pricing extract
Daniel Brennan
10-23-2015
NA




















Functional Requirement


Purpose/WHY:

[Explain the purpose of the project and the reason why this requirement has come]
Particular discount should be override with another discount in the sales order with the value based on order creation date.

In Scope:

[List the activities to be included in scope]
Only US and Canada pricing procedures needs to be configured to override the discount condition.

Out of Scope:

[Out of scope activities]
Other regions pricing procedures are out of scope.

Solution Summary


[Discuss this section with Requester and get approval prior to beginning work]

New condition table,access sequence and condition type must be created and assigned to ZNECAP and ZNECCA pricing procedures.

Add new field to ROC pricing extract:
The program ZISD_EXT_J3AP_Z020 needs to be modified to add new field to display ZDOR condition value.This new value should be considered from SOrg/Material and by SOrg/Season/Collection.


Test Plan

[List test scenarios/cases to be executed here]
Test ID
Test Scenario
Expected Result
1
Create a SO manually with 1000,10,00 sales area with Document date (VBAK - AUDAT) as 10/06/2015.
1.The ZDOR condition values should be considered from the condition validity periods based on the Document date. 2. The Z020 condition should get inactivated in the SO and corresponding invoice and its value should not be calculated on the net value.
2
Create a SO manually with 1000,10,00 sales area with Document date (VBAK - AUDAT) as 10/14/2015.
1.The ZDOR condition values should be considered from the condition validity periods based on the Document date. 2. The Z020 condition should get inactivated in the SO and corresponding invoice and its value should not be calculated on the net value.
3
Create a SO manually with 1000,10,00 sales area with Document date (VBAK - AUDAT) as 10/30/2015.
1.The ZDOR condition type shouldn't be displayed as there is no condition record maintained with the given Document date range. 2. The Z020 condition should be activated in the SO and corresponding invoice and its value should be calculated on the net value.
4
Create a SO through an incoming IDOC with 1000,10,00 sales area with Document date (VBAK - AUDAT) as 10/06/2015.
1.The ZDOR condition values should be considered from the condition validity periods based on the Document date. 2. The Z020 condition should get inactivated in the SO and corresponding invoice and its value should not be calculated on the net value.
Add new field to ROC pricing extract:
S.No
Material
Number of seasons in MM
Test Scenario
Expected Result in the output
Seasons in MM
Valid Record in S.org/Material (A516 )table
Valid Record in S.org/Season/Collection (A525) table
1
10018681
1
Invalid Season - 130 / 2493
Yes
No
Value should be considered from A516 table
2
10019022
1
Invalid Season - 130 / 2496
No
Yes
No value should be displayed
3
10019025
1
Invalid Season - 130 / 2497
Yes
Yes
Value should be considered from A516 table
4
10019026
1
Invalid Season - 130 / 2609
No
No
No value should be displayed
5
10019031
1
Valid season - 360 / 3398
Yes
No
Value should be considered from A516 table
6
10019033
1
Valid season - 360 / 3399
No
Yes
Value should be considered from A525 table
7
10019035
1
Valid season - 360 / 3400
Yes
Yes
Value should be considered from A516 table
8
10019037
1
Valid season - 360 / 3401
No
No
No value should be displayed
9
10019052
2
One valid - 360 / 3398
One invalid - 130 / 2493
Yes
No
Value should be considered from A516 table
10
10019053
2
One valid - 360 / 3399
One invalid - 130 / 2496
No
Yes
(valid record mainatined for 360/3399 season/collection)
(valid record mainatined for 130 /2496 season/collection)
Value should be considered from A525 table for 360 / 3399 season and collection
11
10019054
2
One valid - 360 / 3400
One invalid - 130 / 2497
Yes
Yes
Value should be considered from A516 table
12
10019055
2
One valid - 360 / 3401
One invalid - 130 / 2609
No
No
No value should be displayed
13
10019056
2
Two valid seasons
360 / 3402
360 / 3403
Yes
No
Value should be considered from A516 table
14
10019057
2
Two valid seasons
360 / 3404
360 / 3405
No
Yes
(valid record mainatined for 360/3404 season/collection)
(invalid record mainatined for 360 / 3405 season/collection)
Value should be considered from A525 table for 360/3404 season/collection
15
10019058
2
Two valid seasons
360 / 3406
360 / 3407
No
Yes
(valid record mainatined for 360/3406 season/collection)
(valid record mainatined for 360/3407 season/collection)
Value should be considered from A525 table for 360/3406 season/collection
16
10019059
2
Two valid seasons
360 / 3408
360 / 3409
Yes
Yes
Value should be considered from A516 table
17
10019062
2
Two valid seasons
360 / 3410
360 / 3411
No
No
No value should be displayed

Solution Details


[Provide complete technical details for configuration or programming here]
1. New condition table A525 Sales org./Season/Collection is created .
2. New access sequence ZDOR is created and the above condition table is assigned as below to the access sequence.



ZDOR Access sequence and Cond.tab assignment.jpg

3. New Condition type ZDOR is created with below configuration.

ZDOR Condition type Config1.jpg

ZDOR Condition type Config2.jpg

4.Assign ZDOR to exclusion group to inactivate Z020 pricing condiiton in SO pricing for both ZNECAP and ZNECCA pricing procedures.

5. Assign ZDOR pricing condition type to ZNECAP and ZNECCA pricing procedures.


ZNECAP PP.jpg




5. The ZDOR condition type is assigned to COPA .


Assign ZDOR to CO-PA.jpg

Add new field to ROC pricing extract:



Issues


[List Issues / Bugs identified in configuration or development]